Multi-Endpoint Adapter/Multi-Processor Packet Routing System

ABSTRACT

A multi-endpoint adapter includes endpoints configured to couple to respective processing subsystems, multi-endpoint adapter ports configured to couple to an external switch via respective external switch ports, and an internal switch coupled to the endpoints and multi-endpoint adapter ports. The internal switch receives a data packet from a first application provided by a first processing subsystem through a first endpoint, and matches the data packet to a data flow associated with QoS parameter(s). The internal switch then identifies a data flow action that is associated with the data flow and that provides for the transmission of the data packet via a first multiple endpoint adapter port that is configured in a manner that satisfies the at least one QoS parameter, and performs the data flow action to transmit the data packet through the first multi-endpoint adapter port and a first external switch port to the external switch.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to routing packets via a multi-endpointadapter device coupled to multiple processing subsystems in aninformation handling system.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Some information handling systems such as, for example, server devices,include multiple processors and utilize a Non-Uniform Memory Access(NUMA) computer memory design in which each processor is provided alocal memory that it can access quickly, with those processors coupledtogether via processor interconnect(s) (e.g., Ultra-Path Interconnects(UPIs) available in processing systems provided by INTEL® Corporation ofSanta Clara, Calif., United States) that allow the processors to accessthe memory that is local to the other processors. Furthermore, suchserver devices may be provided with multi-endpoint adapter devices thatprovide a plurality of endpoints (e.g., PCIe endpoints), and in aspecific example the endpoints may include software-defined NetworkInterface Controllers (NICs). When each of the endpoints is connected toa respective processor by a dedicated link (e.g., a PCIe bus), itbecomes desirable to prevent applications (e.g., provided by eachrespective processor executing application code stored in its respectivelocal memory) from sending data packets over the processorinterconnect(s), as doing so introduces latency in the transmission ofthose data packets and can use up the bandwidth of the processorinterconnect(s) and prevent or limit the intended use of those processorinterconnect(s) for direct memory accesses by the processors accessingmemory that is local to another processor.

Multi-endpoint adapter devices have been developed that prevent datapackets generated by the applications discussed above from beingtransmitted over the processor interconnects, including those describedin U.S. patent Ser. No. 15/872,100, filed on Jan. 16, 2018, thedisclosure of which is incorporated by reference herein in its entirety.However, such multi-endpoint adapter do not take into account Quality ofService (QoS) considerations for data packets routed from applicationsto an external switch such as, for example, a Top Of Rack (TOR) switch.For example, many application are provided according to Service LevelAgreements (SLAs) that guarantee a minimum bandwidth and/or maximumlatency associated with their data packet transmissions, and while themulti-endpoint adapter devices discussed above reduce latency bypreventing the use of the processor interconnects to transmit datapackets from the applications to the external switch, they provide nocontrol over the NICs and therefore cannot route data packets in amanner that can guarantee QoS requirements provided for thoseapplications.

Accordingly, it would be desirable to provide an improved multi-endpointadapter/multi-processor packet routing system.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a plurality of memory subsystems; a respective processingsubsystem coupled to each of the plurality of memory subsystems, whereineach respective processing subsystem is configured to executeinstructions that are included on the respective memory subsystem towhich it is coupled in order to provide a respective application; and amulti-endpoint adapter device that is coupled to each of the respectiveprocessing subsystems, wherein the multi-endpoint adapter deviceincludes: a respective endpoint device coupled to each respectiveprocessing subsystem; a plurality of multi-endpoint adapter device portsthat are coupled to respective external switch device ports on anexternal switch device; and an internal switch device that is coupled toeach of the respective endpoint devices and each of the plurality ofmulti-endpoint adapter device ports, wherein the internal switch deviceis configured to: receive, from a first application provided by a firstprocessing subsystem and through a first endpoint device, a data packet;match the data packet to a data flow that is identified in an internalswitch device database and that is associated with at least one Qualityof Service (QoS) parameter; identify a data flow action that isassociated with the data flow in the internal switch device database andthat provides for the transmission of the data packet via a firstmulti-endpoint adapter device port that is included in the plurality ofmulti-endpoint adapter device ports and that is configured in a mannerthat satisfies the at least one QoS parameter; and perform the data flowaction to transmit the data packet through the first multi-endpointadapter device port to the external switch device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an InformationHandling System (IHS).

FIG. 2 is a schematic view illustrating an embodiment of a networkedsystem including an embodiment of the multi-endpointadapter/multi-processor packet routing system of the present disclosure.

FIG. 3 is a schematic view illustrating an embodiment of a switch deviceand a server device that may be provided in the networked system of FIG.2.

FIG. 4 is a flow chart illustrating an embodiment of a method forrouting packets in a multi-endpoint adapter/multi-processor system.

FIG. 5 is a swim lane diagram illustrated an embodiment of theconfiguration of the multi-endpoint adapter/multi-processor systemprovided by the switch device and the server device of FIG. 3 during themethod of FIG. 4.

FIG. 6A is a schematic view illustrating an embodiment of configurationoperations of the multi-endpoint adapter/multi-processor system providedby the switch device and the server device of FIG. 3 during the methodof FIG. 4.

FIG. 6B is a schematic view illustrating an embodiment of theconfiguration operations of the multi-endpoint adapter/multi-processorsystem provided by the switch device and the server device of FIG. 3during the method of FIG. 4.

FIG. 6C is a schematic view illustrating an embodiment of theconfiguration operations of the multi-endpoint adapter/multi-processorsystem provided by the switch device and the server device of FIG. 3during the method of FIG. 4.

FIG. 7A is a schematic view illustrating an embodiment of the datapacket routing operations of the multi-endpoint adapter/multi-processorsystem in the server device of FIG. 3 during the method of FIG. 4.

FIG. 7B is a schematic view illustrating an embodiment of the datapacket routing operations of the multi-endpoint adapter/multi-processorsystem provided by the switch device and the server device of FIG. 3during the method of FIG. 4.

FIG. 7C is a schematic view illustrating an embodiment of the datapacket routing operations of the multi-endpoint adapter/multi-processorsystem provided by the switch device and the server device of FIG. 3during the method of FIG. 4.

FIG. 7D is a schematic view illustrating an embodiment of the datapacket routing operations of the multi-endpoint adapter/multi-processorsystem provided by the switch device and the server device of FIG. 3during the method of FIG. 4.

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIG. 2, an embodiment of a networked system 200 isillustrated that provides an embodiment of the multi-endpointadapter/multi-processor packet routing system of the present disclosure.In the illustrated embodiment, the system 200 includes a SoftwareDefined Networking (SDN) orchestrator subsystem 202 that is coupledthrough an SDN controller subsystem 204 to an external switch devicesuch as, for example, the Top Of Rack (TOR) switch device 206illustrated in FIG. 2. In some embodiments, the SDN orchestratorsubsystem 202 and the SDN controller subsystem 204 may be provided aspart of the TOR switch device 206 via, for example, applicationsprovided in, and/or hardware included in, the TOR switch device 206.However, in other embodiments the SDN orchestrator subsystem 202 and/orthe SDN controller subsystem 204 may be provided in device(s) that areseparate from the TOR switch device 206 (or other external switchdevice) while remaining within the scope of the present disclosure aswell.

As would be understood by one of skill in the art in possession of thepresent disclosure, SDN orchestrator subsystems may be provided bysoftware and/or hardware that operates via a management plane to providelife-cycle management for an SDN network, as well as perform other SDNorchestration functionality known in the art, while SDN controllersubsystems may be provided by software and/or hardware that operates viaa control plane to implement control plane functionality for an SDNnetwork, as well as perform other SDN controller functionality known inthe art. The TOR switch device 206 and/or any device(s) providing theSDN orchestrator subsystem 202 and the SDN controller subsystem 204 maybe provided by the IHS 100 discussed above with reference to FIG. 1,and/or may include some or all of the components of the IHS 100.However, while illustrated and discussed as a TOR switch device 206, oneof skill in the art in possession of the present disclosure willrecognize that the devices included in the networked system 200 toprovide the multi-endpoint adapter/multi-processor packet routing systemof the present disclosure may include any devices that may be configuredto operate similarly as discussed below.

As illustrated, the TOR switch device 206 is coupled to a server device208 that includes the multiple processor subsystems and multi-endpointadapter device of the present disclosure, which as discussed belowprovide for the multi-endpoint adapter/multi-processor packet routingfunctionality described herein. The server device 208 may be provided bythe IHS 100 discussed above with reference to FIG. 1, and/or may includesome or all of the components of the IHS 100. While a single externalswitch device (referred to as “external” because, in this example, theTOR switch device 206 is external to the server device 208) and a singleserver device are illustrated, one of skill in the art in possession ofthe present disclosure will recognize that many more external switchdevices and server devices may (and typically will) be coupled togetherand provided in the networked system 200 (e.g., an a datacenter) whileremaining within the scope of the present disclosure. While a specificnetworked system 200 has been illustrated and described, one of skill inthe art in possession of the present disclosure will recognize that thenetworked system of the present disclosure may include a variety ofcomponents and/or component configurations while remaining within thescope of the present disclosure as well.

Referring now to FIG. 3, an embodiment of the multi-endpointadapter/multi-processor packet routing system of the present disclosureis illustrated as provided by a TOR switch device 300 (which may be theTOR switch device 206 discussed above with reference to FIG. 2) coupledto a server device 302 (which may be the server device 208 discussedabove with reference to FIG. 2.) As such, the TOR switch device 300 maybe provided by the IHS 100 discussed above with reference to FIG. 1and/or may include some or all of the components of the IHS 100, and asdiscussed above may be considered as an “external” switch device fromthe point of view of the server device 302. In the illustratedembodiment, the TOR switch device 300 includes a plurality of TOR switchdevice ports 300 a and 300 b (i.e., external switch device ports) that,as discussed below, are configured to couple the TOR switch device 300to the server device 302. Furthermore, while illustrated and discussedas a TOR device 300, one of skill in the art in possession of thepresent disclosure will recognize that the functionality of the TORswitch device 300 discussed below may be provided by other devices thatare configured to operate similarly as discussed below.

The server device 302 may also be provided by the IHS 100 discussedabove with reference to FIG. 1 and/or may include some or all of thecomponents of the IHS 100. Furthermore, while illustrated and discussedas a server device 302, one of skill in the art in possession of thepresent disclosure will recognize that the functionality of the serverdevice 302 discussed below may be provided by other devices that areconfigured to operate similarly as discussed below. In the illustratedembodiment, the server device 302 includes a chassis 304 that houses thecomponents of the server device 300, only some of which are illustratedbelow. For example, the chassis 304 may house a processing system that,in the illustrated embodiment, includes a plurality of processingsubsystems 306 a and 308 a (which may each include one or more of theprocessor 102 discussed above with reference to FIG. 1) that are coupledtogether by a processor interconnect 310 such as, for example, anUltra-Path Interconnect (UPI) available in processing systems providedby INTEL® Corporation of Santa Clara, Calif., United States.

In the illustrated embodiment, each of the processing subsystems 306 aand 308 a are provided with and connected to respective memorysubsystems 306 b and 308 b. For example, the processing subsystems andmemory subsystems in the server device 300 may utilize a Non-UniformMemory Access (NUMA) computer memory design in which each respectiveprocessing subsystem is connected a respective local memory subsystem toprovide a respective NUMA node (i.e., the processing subsystem 306 a andits local memory subsystem 306 b provide a first NUMA node, and theprocessing subsystem 308 a and its local memory subsystem 308 b providea second NUMA node.) However, while two processing subsystems/memorysubsystems (e.g., two NUMA nodes) are illustrated in FIG. 3, one ofskill in the art in possession of the present disclosure will recognizethat additional processing subsystems/memory subsystems (e.g., NUMAnodes) may be provided according to the teachings of the presentdisclosure will falling within its scope as well

The chassis 302 may also house a multi-endpoint adapter device 312 thatmay provide, for example, the Network Interface Controller (NIC)functionality discussed below, although one of skill in the art inpossession of the present disclosure will recognize that othermulti-endpoint adapter device functionality will fall within the scopeof the present disclosure as well. In the illustrated embodiment, themulti-endpoint adapter device 312 includes a plurality of multi-endpointadapter device ports 314 a and 314 b that may be provided by, forexample, Ethernet ports that are configured to couple the multi-endpointadapter device 312 (and thus the server device 302 in which it isprovided) to the TOR switch device 300. In the illustrated embodiment, aplurality of transceivers 316 a and 316 b (e.g., Quad Small Form-factorPluggable (QSFP) transceivers) are connected to each of themulti-endpoint adapter device ports 314 a and 314 b, respectively, andare also coupled to the TOR switch device ports 300 a and 300 b,respectively, in order to couple the multi-endpoint adapter device312/server device 302 to the TOR switch device 300. However, while aspecific coupling configuration with transceivers is illustrated anddescribed, one of skill in the art in possession of the presentdisclosure will recognize that the multi-endpoint adapter device312/server device 302 may be coupled to the TOR switch device300/external switch device in a variety of manners that will fall withinthe scope of the present disclosure as well.

In the illustrated embodiment, the multi-endpoint adapter device 312includes a NIC controller 318 that is coupled to each of themulti-endpoint adapter device ports 314 a and 314 b and that, asdiscussed below, may be provided by a “smart” NIC controller that iscapable of configuring (or providing for the configuration of)subsystems on the multi-endpoint adapter device 312. In the illustratedembodiment, the multi-endpoint adapter device 312 also includes internalswitch device 320 that is coupled to each of the multi-endpoint adapterdevice ports 314 a and 314 b and to the NIC controller 318. As discussedbelow, the multi-endpoint adapter device 312 may be configured by theNIC controller 318 to perform the data packet routing discussed below.In the illustrated embodiment, the multi-endpoint adapter device 312also includes a plurality of Media Access Control (MAC) controllers 322a and 322 b that are coupled to the internal switch device 320 and thatmay include, for example, hardware that provides for the implementationof the MAC sublayer in the data link layer that provides for addressingand channel access control mechanisms. In the illustrated embodiment,the multi-endpoint adapter device 312 also includes a plurality ofendpoint devices 324 a and 324 b that are coupled to the MAC controllers322 a and 322 b, respectively, and that may each be provided by, forexample, physical or virtual Peripheral Component Interconnect express(PCIe) devices, although one of skill in the art in possession of thepresent disclosure will recognize that other types of endpoint devicesmay fall within the scope of the present disclosure as well.

Each of the endpoint devices 324 a and 324 b are coupled to a physicallayer (PHY) device 326 that may be provided with (or as part of) aconnector (not illustrated, but which may be provided by a PCIeconnector) on the multi-endpoint adapter device 312. The PHY device 326is configured to connect to a board (e.g., a motherboard) in the chassis304 (e.g., via a riser device), which may provide for one or moreconnections to the processing subsystems 306 a/306 b and memorysubsystems 308 a and 308 b in order to couple the multi-endpoint adapterdevice 312 to the processing subsystems 306 a and 306 b (e.g., via aPCIe bus provided on the board and PCIe root ports included in theprocessing subsystems 306 a and 306 b). In some embodiments, thecoupling of the multi-endpoint adapter device 312 to the processingsubsystems 306 a and 306 b may include a single connection 328 betweenthe processing subsystem 306 a and the PHY device 326. However, in someembodiments, the coupling of the multi-endpoint adapter device 312 tothe processing subsystems 306 a and 306 b may also include a dedicatedconnection 330 (illustrated in dashed lines in FIG. 3 to indicate thatthat it is optional in some embodiments) between the processingsubsystem 308 a and the PHY device 326. While a specific server device302 has been illustrated, one of skill in the art in possession of thepresent disclosure will recognize that server devices (or other devicesoperating according to the teachings of the present disclosure in amanner similar to that described below for the server device 300) mayinclude a variety of components and/or component configurations forproviding conventional server device functionality, as well as thefunctionality discussed below, while remaining within the scope of thepresent disclosure as well.

Referring now to FIG. 4, an embodiment of a method for routing packetsin a multi-endpoint adapter/multi-processor system is illustrated. Asdiscussed below, the systems and methods of the present disclosureprovide for the configuration of a multi-endpoint adapter device toprovide for the transmission of data packets via the multi-endpointadapter device in a manner that ensures a Quality of Service (QoS)guaranteed to an application that provided those data packets. Forexample, Software Defined Networking (SDN) control subsystems (e.g.; anorchestrator and a controller) may be provided with data packet routingconfigurations that may be based on QoS guarantees for applications thatare provided by processing subsystems in the server device that includesthe multi-endpoint adapter device. The SDN control systems may transmitthe data packet routing configurations via an external switch device,such as a TOR switch, to the multi-endpoint adapter device in the serverdevice, where they are received by a MC controller included on themulti-endpoint adapter device. The NIC controller uses the data packetrouting configurations to configure an internal switch device includedon the multi-endpoint adapter device, which may include providing dataflow match information and data flow action information for storage inan internal switch device database that is accessible to the internalswitch device, programming a flow database that is accessible to theinternal switch device with information for forwarding data packets,causing the internal switch device to negotiate port speeds formulti-endpoint adapter device ports on the multi-endpoint adapter devicethat are coupled to the external switch device, and/or performing avariety of other configuration operations that would be apparent to oneof skill in the art in possession of the present disclosure.

Subsequently, when the internal switch device receives data packets fromapplications provided by the processing subsystems in the server device;it uses the data flow matching information to match those data packetsto particular data flows, and uses the data flow action information todetermine data flow actions that are associated with those data flowsand that provide for the transmission of their associated data packetsin a manner that satisfies the QoS guarantees for the applications thatgenerated them. The internal switch device may then transmit each datapacket it received according to the data flow action identified for thedata flow that matches that data packet, which ensures that each datapacket generated by an application provided by a processing subsystem inthe server device will be transmitted from the server device to theexternal switch device via the multi-endpoint adapter device ports onthe multi-endpoint adapter device that are configured to satisfy the QoSguarantee associated with the application that generated that datapacket. As such, the teachings of the present disclosure provide datapacket transmission systems that may save power by ensuring that datapackets are not transmitted at higher speeds than are required, conserveexternal switch device processing, frequency, and, load resources, workaround “noisy neighbor” applications that attempt to utilize datatransmission resources they do not require, and/or provide a variety ofother benefits that would be apparent to one of skill in the art inpossession of the present disclosure.

The method 400 begins at block 402 where an SDN controller subsystemprovides data packet routing configuration information to amulti-endpoint adapter device via an external switch device. In anembodiment, at or before block 402, the SDN orchestrator subsystem 202may receive application Quality of Service (QoS) information. Forexample, the SDN orchestrator subsystem 202 may provide an QoSprovisioning application that is accessible to an administrator or otheruser, and may provide (e.g., via a graphical user interface displayed ona display device) for the input of QoS information that, in the examplesbelow, define how data packets generated by particular applicationsshould be transmitted by a multi-endpoint adapter device in order tosatisfy QoS guarantees provided for those applications. For example, theSDN orchestration subsystem 202 may allow for the provisioning of anapplication identifier that identifies an application, as well one ormore QoS parameters that define the QoS guaranteed for the provisioningof that application by a server device. However, while described asbeing provided by an administrator or other user, the QoS informationprovided by the SDN orchestration subsystem 202 to the SDN controllersubsystem 204 as discussed below may be received by the SDNorchestration subsystem in other manners, may be dynamically determinedby the SDN orchestration subsystem, and/or may be generated in any of avariety of manners that would be apparent to one of skill in the art inpossession of the present disclosure.

In the specific examples discussed below, the QoS parameters define afirst QoS for an application 600 that is provided by the processingsubsystem 306 a (e.g., via the execution of application code included inthe memory subsystem 306 b), and a second QoS for an application 602that is provided by the processing subsystem 308 a (e.g., via theexecution of application code included in the memory subsystem 308 b),with those the QoS configured to guarantee a minimum data packettransmission bandwidth (e.g., 10 Gbps, 25 Gbps, and 10+25 Gbps in theexamples below). However, in other embodiments the QoS guarantees mayprovide for a maximum latency. Furthermore, in some embodiments, otherQoS parameters may not be related to data transmission while remainingwithin the scope of the present disclosure as well.

As such, at or prior to block 402, the SDN orchestration subsystem 202may provide the QoS information to the SDN controller subsystem 204(e.g., via a “north-south” Application Programming Interface (API)).With reference to FIG. 5, the SDN orchestrator subsystem 202 isillustrated as providing the QoS information to the SDN controllersubsystem 204 in a MC configuration change request 500. In addition,FIG. 5 illustrates how the SDN orchestrator subsystem 202 may provide aTOR configuration change request 502 to the SON controller subsystem204, which may operate to request a configuration of the TOR switchdevice 300 in a manner that provides for the satisfaction of the QoSguarantees discussed above. For example, the configuration request forthe TOR switch device 300 may request the configuration of speedsettings on one or more ports on the TOR switch device 300, MaximumTransmission Unit (MTU) settings, Virtual Local Area Network (ULAN)settings, optimal payload fragmentation settings, payload bufferingconfigurations, and/or other TOR switch device settings that would beapparent to one of skill in the art in possession of the presentdisclosure. Furthermore, the configuration request for the TOR switchdevice 300 may request the configuration of same flow marchingconfigurations that may be applied on the TOR switch device 300 toidentify flows when forwarding those flows to other switch devices andpreserving end-to-end QoS guarantees.

The SDN controller subsystem 204 may then operate to utilize the QoSinformation to generate data packet routing configuration informationthat, as discussed below, may provide for data packet/data flowmatching, data flow actions that are associated with data flows fromparticular applications and that operate to ensure QoS parameters forthose particular applications, flow database programming that isconfigured to enable data packet routing, and/or any other data packetrouting configuration functionality that would be apparent to one ofskill in the art in possession of the present disclosure as providingfor the functionality discussed below. However, while the SON controllersubsystem 204 is describes as converting QoS information received froman SON orchestration subsystem into data packet routing configurationinformation, one of skill in the art in possession of the presentdisclosure will recognize that the SON controller subsystem 204 mayreceive the data packet routing configuration information directly,generate the data packet routing configuration information in mannersother than via QoS information received from an SON orchestrationsubsystem, and/or provide the data packet routing configurationinformation in a variety of manners that will fall within the scope ofthe present disclosure as well.

In an embodiment, at block 402, the SDN controller subsystem 204 mayoperate to transmit the data packet routing configuration informationthrough the TOR switch device 206/300 to the server device 208/302. Forexample, at block 402, the SDN controller subsystem 204 may provide thedata packet routing configuration information in a Type-Length-Value(TLV) format of OPENFLOW control packet(s) (e.g.,openflow-set-configuration command(s)), which may be provided accordingto the OPENFLOW communications protocol, although the transmission ofthe data packet routing configuration information via othercommunication protocols and/or other techniques will fall within thescope of the present disclosure as well. FIG. 6A illustrates how the TORswitch device 300 may receive data packet routing configurationinformation 604, and provide that data packet routing configurationinformation 604 to the NIC controller 318 via either or both of theexternal switch device ports 300 a, either or both of the transceivers316 a and 316 b, and either or both of the multi-endpoint adapter deviceports 314 a and 314 b. With reference to FIG. 5, the SDN controllersubsystem 204 is illustrated as providing the data packet routingconfiguration information to the NIC controller 318 in a NICconfiguration instruction 504. In addition, FIG. 5 illustrates how theSDN controller subsystem 204 may provide a TOR configuration instruction506 to the NIC controller 318, which may operate to configure the TORswitch device 300 in any manner that provides for the satisfaction ofthe QoS guarantees discussed above. Continuing with the example providedabove, the configuration of the TOR switch device 300 may include theconfiguration of speed settings on one or more ports on the TOR switchdevice 300, Maximum Transmission Unit (MTU) settings, Virtual Local AreaNetwork (ULAN) settings, optimal payload fragmentation settings, payloadbuffering configurations, and/or other TOR switch device settings thatwould be apparent to one of skill in the art in possession of thepresent disclosure. Furthermore, the configuration of the TOR switchdevice 300 may include the configuration of same flow marchingconfigurations for the TOR switch device 300 that identify flows whenforwarding those flows to other switch devices and preserving end-to-endQoS guarantees.

The method 400 then proceeds to block 404 where a NIC controller in themulti-endpoint adapter device configures an internal switch device usingthe data packet routing configuration information. In an embodiment, atblock 404, the NIC controller 318 may operate to configure the internalswitch device 320 using the data packet routing configurationinformation received at block 402. As discussed in further detail below,the configuration of the internal switch device 320 at block 404 mayinvolve a variety of information being provided to and/or stored in adatabase included in and/or accessible to the internal switch device320, a variety of configuration operations being performed on theinternal switch device 302, a variety of other operations that may causethe internal switch device to perform configuration actions on othersubsystems, and/or any other configuration action that would be apparentto one of skill in the art in possession of the present disclosure. Assuch, FIG. 6B illustrates the NIC controller 318 performingconfiguration operations 606 on the internal switch device 320, and FIG.6C illustrates an example in which the configuration operations 606cause the internal switch device 320 to perform configuration operations608 on either or both of the MAC controllers 322 a and 322 b.

For example, at block 404 and as illustrated in FIG. 5, the NICcontroller 318 may utilize the data packet routing configurationinformation to perform NIC configuration operations 508 that may operateto configure the multi-endpoint adapter device 312 in a manner thatprevents the use of the processor interconnect 310 for data packetstransmitted between the endpoint devices 324 a/324 b and theapplications 600/602. For example, as discussed in U.S. patent Ser. No.15/872,100, filed on Jan. 16, 2018, when the respective connections 328and 330 are provided for each of the processing subsystems 306 a and 308a, respectively, to the multi-endpoint adapter device 312 (e.g., via thePHY device 326), it is desirable to configure the multi-endpoint adapterdevice 312 to prevent the use of the processor interconnect 310 for datapackets transmitted between the endpoint devices 324 a/324 b and theapplications 600/602. As such, the NIC configuration operations 508 mayoperate to configure the multi-endpoint adapter device 312 to ensurethat data packet transmissions between the endpoint devices 324 a/324 band the processing subsystem 306 a/308 a occur over the connections 328and 330 and not the processor interconnect 310, which may includereconfiguring a ×16 connection between the processing subsystem 306 aand the endpoint device 324 a (e.g., that is utilized when theconnection 330 is not available) into two ×8 connections between theprocessing subsystems 306 a and 308 and each of the endpoints 324 a and324 b, respectively, (e.g., using the available connections 328 and 330,respectively) that are mapped to root ports (e.g., PCIe root ports) ontheir respective processing subsystems 306 a and 308 a.

In another example, at block 404 and as illustrated in FIG. 5, the MCcontroller 318 may utilize the data packet routing configurationinformation to provide a flow information update 510 to the internalswitch device 320 that may include data flow match information that, asdiscussed below, is configured to allow for the matching of data packetsto data flows that are associated with particular applications (e.g.,the applications 600 and 602 illustrated in FIGS. 6A-60 and 7A-7C).Furthermore, the flow information update 510 may also include data flowaction information that, as discussed below, is configured to providefor the performance of data flow actions on data packets that match dataflows that are associated with particular applications (e.g., theapplications 600 and 602 illustrated in FIGS. 6A-6C and 7A-7C). As wouldbe understood by one of skill in the art in possession of the presentdisclosure, the provisioning of the flow information update 510 mayinclude the programming of rules in the internal switch device 320 thatidentify application data packet flows, provide for actions on datapackets in data packet flows, and/or provide for any other SDNprogramming operations that would be apparent to one of skill in the artin possession of the present disclosure. As such, in some embodiments,the provisioning of the data flow match information and/or data flowaction information to the internal switch device 320 may include storingthat data flow match information and/or data flow action information inan internal switch device database included in the internal switchdevice 320 and/or otherwise accessible to the internal switch device.

In another example, at block 404 and as illustrated in FIG. 5, the NICcontroller 318 may utilize the data packet routing configurationinformation to provide a flow database update 512 to the internal switchdevice 320 that may include updating a flow database table included inthe internal switch device 320 and/or otherwise accessible to theinternal switch device. As will be understood by one of skill in the artin possession of the present disclosure, the flow database table mayprovide for Internet Protocol (IP)/MAC forwarding, and its updating atblock 404 may ensure that data packets are forwarded to a desired MACport, which may provide for the splitting of data traffic received themulti-endpoint adapter device ports 314 a and 314 b between MAC portsthat are mapped to particular endpoint devices 324 a and 324 b, as wellas a variety of other functionality known in the art.

Furthermore, in some embodiments, the internal switch device 320 mayperform other configuration operations as well. For example, at block404, the internal switch device 320 may operate to configure the MACcontrollers 322 a and 322 b by, for example, providing for theconfiguration of link speed settings, Link Layer Discovery Protocol(LLDP) Type-Length-Value (TLV) based configuration of MAC controllers(e.g., the internal switch device 320 may utilize LLDP TLVs to negotiatethe configuration of the MAC controllers), and/or other configurationoperations that would be apparent to one of skill in the art inpossession of the present disclosure.

In another example, at block 404, the internal switch device 320 mayprovide for negotiations between the multi-endpoint adapter device port314 a and/or transceiver 316 a and the external switch device port 300 aon the external switch device 300 in order to configure themulti-endpoint adapter device port 314 a and/or transceiver 316 a toprovide a 25 Gbps data transmission speed with the external switchdevice port 300 a. In another example, the internal switch device 320may provide for negotiations between the multi-endpoint adapter deviceport 314 b and/or transceiver 316 b with the external switch device port300 b on the external switch device 300 in order to configure themulti-endpoint adapter device port 314 b and/or transceiver 316 b toprovide a 10 Gbps data transmission speed with the external switchdevice port 300 b. In yet another example, the internal switch device320 may perform bonding, teaming, trunking, and/or other aggregationtechniques on the multi-endpoint adapter device port 314 a/transceiver316 a and the multi-endpoint adapter device port 314 b/transceiver 316 bin order to provide an aggregated link between the multi-endpointadapter device 312 and the external switch device 300 (which, asdiscussed below, may provide a 10+25 Gpbs data transmission speed usingthe examples above).

While a few specific examples of the configuration of the internalswitch device 320 and other subsystems in the multi-endpoint adapterdevice 312 have been described, one of skill in the art in possession ofthe present disclosure will recognize that a variety of configurationsmay be performed on the multi-endpoint adapter device 312 at block 404in order to provide for the functionality discussed below whileremaining within the scope of the present disclosure as well.

The method then proceeds to block 406 where the internal switch devicereceives a data packet from an application and matches the data packetto a data flow. In an embodiment, at block 406 and as illustrated inFIG. 7A, the application 602 may operate to generate a data packet 700and transmit that data packet 700. As discussed above, the application602 and multi-endpoint adapter device 312 may be configured to preventthe applications 600 and 602 from providing data packets via theprocessor interconnect 310 and, as such, the data packet 700 generatedby the application 602 is transmitted by the processing subsystem 308 ato the PHY device 326 via the connection 330 such that it is received bythe endpoint device 324 b, which provides the data packet 700 throughthe MAC controller 322 b to the internal switch device 320. While notillustrated or discussed in detail, one of skill in the art inpossession of the present disclosure will recognize that the application600 may transmit data packets in a similar manner such that those datapackets are transmitted by the processing subsystem 306 a to the PHYdevice 326 via the connection 328 and received by the endpoint device324 a, which then provides those data packets through the MAC controller322 a to the internal switch device 320.

In an embodiment, at block 406 and upon receiving the data packet 700,the internal switch device 320 may operate to compare informationincluded in the data packet 700 with the data packet flow informationthat was provided to the internal switch device 320 (e.g., in theinternal switch device database as discussed above) at block 404, andidentify a data flow in the data packet flow information that matchesthe data packet that was received at block 406. As would be understoodby one of skill in the art in possession of the present disclosure, adata flow may be made up of a plurality of data packets, and commoninformation may be included in each of those data packets that belong tothe same data flow, which allows the inspection of any particular datapacket in order to match its data packet information to a data flow(i.e., when that data flow is identified as discussed above via the datapacket flow information.) In a specific example, an applicationgenerating the data packet received at block 406 may provide a varietyof data packet information in that data packet that allows for thematching of that data packet to a data flow including, for example, aMAC address of the source/destination peers, a VLAN tag that identifiesthe network resource group to which the QoS policy will be applied, abandwidth setting that provides for settings such as maximumavailable/minimum available/best effort/minimum guarantee, an IP addressof the source/destination peers, a port number of the workload server,and/or any other data packet information that would be apparent to oneof skill in the art in possession of the present disclosure. As such,continuing with the example provided above, the internal switch device320 may determine that the data packet 700 received at block 406 matchesa data flow that is provided by the application 602 by, for example,determining that the data packet 700 includes a VLAN tag that matches aVLAN tag for data flows provided by the application 602.

The method then proceeds to block 408 where the internal switch deviceidentifies a data flow action associated with the data flow. In anembodiment, at block 408 and upon identifying the data flow to which thedata packet 700 belongs, the internal switch device 320 may operate toaccess the data flow action information that was provided to theinternal switch device 320 (e.g., in the internal switch device databaseas discussed above) at block 404, and identify at least one data flowaction associated with that data flow. As discussed above and for thepurposes of the examples below, the multi-endpoint adapter device port314 a and/or transceiver 316 a may have been configured to provide a 25Gbps data transmission speed with the external switch device port 300 aon the external switch device 300, while the multi-endpoint adapterdevice port 314 b and/or transceiver 316 b may have been configured toprovide a 10 Gbps data transmission speed with the external switchdevice port 300 b on the external switch device 300. Furthermore, insome examples, the multi-endpoint adapter device port 314 a/transceiver316 a and the multi-endpoint adapter device port 31412/transceiver 316 bmay have been aggregated via bonding, teaming, trunking, and/or otheraggregation techniques that would be apparent to one of skill in the artin possession of the present disclosure.

In an example of block 408, the data flow action identified at block 408may provide for the transmittal of data packets that are part of thatdata flow via the multi-endpoint adapter device port 314 b because, forexample, the data flow is provided from the application 602 that isassociated with QoS parameters that require a minimum 10 Gbps datapacket transmission speed for data packets that are part of its dataflow(s). In another example of block 408, the data flow actionidentified at block 408 may provide for the transmittal of data packetsthat are part of that data flow via the multi-endpoint adapter deviceport 314 a because, for example, the data flow is provided from theapplication 602 that is associated with QoS parameters that require aminimum 25 Gbps data packet transmission speed for data packets that arepart of its data flow(s). In yet another example, the data flow actionidentified at block 408 may provide for the transmittal of data packetsthat are part of that data flow via the aggregated multi-endpointadapter device ports 314 a and 314 b because, for example, the data flowis provided from the application 602 that is associated with QoSparameters that require a minimum 35 Gbps data packet transmission speedfor data packets that are part of its data flow(s). While the examplesprovided herein are directed to data flow actions that transmit datapackets that match a data flow at particular minimum data packettransmission speeds, as discussed below other data flow actions may beprovided for data packets that are part of a data flow (e.g.,transmission of those data packets at a maximum latency, or evennon-data-packet transmission actions in some embodiments) whileremaining within the scope of the present disclosure.

The method 400 then proceeds to block 410 where the internal switchdevice performs the data flow action on the data packet. In anembodiment, at block 406, the internal switch device 320 operates totransmit the data packet 700 received at block 406 according to the dataflow action determined at block 408. Continuing with the examples above,and with reference to FIG. 78, the internal switch device 320 mayperform the data flow action identified at block 408 to transmit thedata packet 700 via the multi-endpoint adapter device port 314 bbecause, as discussed above, the data packet was received from theapplication 602 that is associated with QoS parameters that require aminimum 10 Gbps data packet transmission speed for data packets that arepart of its data flow(s), and the multi-endpoint adapter device port 314b has been configured to provide 10 Gbps data transmission speeds.Similarly, and with reference to FIG. 70, the internal switch device 320may perform the data flow action identified at block 408 to transmit thedata packet 700 via the multi-endpoint adapter device port 314 abecause, as discussed above, the data packet was received from theapplication 602 that is associated with QoS parameters that require aminimum 25 Gbps data packet transmission speed for data packets that arepart of its data flow(s), and the multi-endpoint adapter device port 314a has been configured to provide 25 Gbps data transmission speeds

With reference to FIG. 7D, the internal switch device 320 may performthe data flow action identified at block 408 to transmit the data packet700 via either of the aggregated multi-endpoint adapter device ports 314a and 314 b because, as discussed above, the data flow was received fromthe application 602 that is associated with QoS parameters that requirea minimum 30 Gbps data packet transmission speed for data packets thatare part of its data flow(s), and the multi-endpoint adapter deviceports 314 a and 314 b has been configured (e.g., aggregated) to provide10+25 Gbps data transmission speeds.

While examples for the transmission of data packets generated by theapplication 602 have been provided, one of skill in the art inpossession of the present disclosure will recognize that data packetstransmitted by the application 600 may be transmitted in a similarmanner as well. Furthermore, one of skill in the art in possession ofthe present disclosure will recognize how data flows from each of theapplications 600 and 602 may be handled by the internal switch device320 to ensure QoS guarantees are satisfied for both by, for example,preventing “noisy neighbor” problems in which one of those applicationwould otherwise utilize data transmission bandwidth that is not calledfor according to its QoS parameters (e.g., with the internal switchdevice 320 preventing that from occurring with knowledge that the otherapplication requires that bandwidth based on its QoS parameters.)Similarly, one of skill in the art in possession of the presentdisclosure will recognize how power savings and external switch deviceprocessing/frequency/load resource use efficiencies may be realized withthe teachings of the present disclosure, as the internal switch device320 is may be configured to ensure that applications only utilize thedata packet transmission bandwidth that is required by their QoSguarantees. Furthermore, the QoS configurations provided as discussedabove may be persistent with the socket direct domain requirements forthe applications, irrespective of changes in the external networktopology and/or unchanged external network wiring.

Thus, systems and methods have been described that provide for theconfiguration of a multi-endpoint adapter device to provide for thetransmission of data packets via the multi-endpoint adapter device in amanner that ensures a Quality of Service (QoS) guaranteed to anapplication that provided those data packets. As such, an internalswitch device on the multi-endpoint adapter device may be configuredsuch that the internal switch device receives data packets fromapplications and uses data flow matching information to match those datapackets to particular data flows, while using data flow actioninformation to determine data flow actions that are associated withthose data flows and that provide for the transmission of theirassociated data packets in a manner that satisfies the QoS guaranteesfor the applications that generated them. The internal switch device maythen transmit each data packet it received according to the data flowaction identified for the data flow that matches that data packet, whichensures that each data packet generated by an application will betransmitted to an external switch device via the multi-endpoint adapterdevice ports on the multi-endpoint adapter device that are configured tosatisfy the QoS guarantee associated with that data packet. As such, theteachings of the present disclosure provide data packet transmissionsystems that may save power by ensuring that data packets are nottransmitted at higher speeds than are required, conserve external switchdevice processing, frequency, and, load resources, work around “noisyneighbor” applications that attempt to utilize transmission resourcesthey do not require, and/or provide a variety of other benefits thatwould be apparent to one of skill in the art in possession of thepresent disclosure.

Furthermore, the present disclosure is being filed along with U.S.patent application Ser. No. ______, attorney docket number16356.2030US01, filed on Apr. 26, 2019, and directed to virtual machinedeployment techniques; U.S. patent application Ser. No. ______, attorneydocket number 16356.2031US01, filed on Apr. 26, 2019, and directed todata splitting techniques; U.S. patent application Ser. No. ______,attorney docket number 16356.2032U501, filed on Apr. 26, 2019, anddirected to data duplicating techniques; U.S. patent application Ser.No. ______, attorney docket number 16356.2034US01, filed on Apr. 26,2019, and directed to communication coupling configuration techniques;U.S. patent application Ser. No. ______, attorney docket number16356.2035U501, filed on Apr. 26, 2019, and directed to connectionconfiguration techniques; and U.S. patent application Ser. No. ______,attorney docket number 16356.2036U501, filed on Apr. 26, 2019, anddirected to sideband communication techniques; each of which includeembodiments that utilize the multi-processor/multi-endpoint systemsdescribed in some of the embodiments included in the present disclosure.One of skill in the art in possession of the present disclosure willrecognize how embodiments of the present disclosure may be combined withsome or all of the disclosures discussed above, and thus thosedisclosures are incorporated by reference herein in their entirety.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. A multi-endpoint adapter device, comprising: aplurality of endpoint devices that are each configured to coupled to arespective processing subsystem; a plurality of multi-endpoint adapterdevice ports that are each configured to couple to respective externalswitch device ports on an external switch device; and an internal switchdevice that is coupled to each of the plurality of endpoint devices andeach of the plurality of multi-endpoint adapter device ports, whereinthe internal switch device is configured to: receive, from a firstapplication that is provided by a first processing subsystem included inthe plurality of processing subsystems and through a first endpointdevice included in the plurality of endpoint devices, a data packet;match the data packet to a data flow that is identified in an internalswitch device database and that is associated with at least one Qualityof Service (QoS) parameter; identify a data flow action that isassociated with the data flow in the internal switch device database andthat provides for the transmission of the data packet via a firstmulti-endpoint adapter device port that is included in the plurality ofmulti-endpoint adapter device ports and that is configured in a mannerthat satisfies the at least one QoS parameter; and perform the data flowaction to transmit the data packet through the first multi-endpointadapter device port to the external switch device.
 2. The multi-endpointadapter device of claim 1, further comprising: a controller that iscoupled to at least one of the plurality of multi-endpoint adapterdevice ports, wherein the controller is configured to: receive, via atleast one of the plurality of multi-endpoint adapter device ports andvia the external switch device, data flow match information; store thedata flow match information in the internal switch device database,wherein the internal switch device is configured to use the data flowmatch information to match the data packet to the data flow.
 3. Themulti-endpoint adapter device of claim 1, further comprising: acontroller that is coupled to at least one of the plurality ofmulti-endpoint adapter device ports, wherein the controller isconfigured to: receive, via at least one of the plurality ofmulti-endpoint adapter device ports and via the external switch device,data flow action information; store the data flow action information inthe internal switch device database, wherein the internal switch deviceis configured to identify the data flow action from the data flow actioninformation.
 4. The multi-endpoint adapter device of claim 1, whereinthe internal switch device is configured to: provide for a negotiationbetween the first multi-endpoint adapter device port and a firstexternal switch device port that configures the first multi-endpointadapter device port the manner that satisfies the at least one QoSparameter.
 5. The multi-endpoint adapter device of claim 1, wherein thematching the data packet to the data flow that is identified in theinternal switch device database includes: identifying a Virtual LocalArea Network (VLAN) tag that was provided in the data packet by thefirst application; matching the VLAN tag to a VLAN tag that isassociated with the data flow in the internal switch device database. 6.The multi-endpoint adapter device of claim 1, wherein the at least oneQoS parameter includes a minimum transmission speed.
 7. An InformationHandling System (IHS), comprising: a plurality of memory subsystems; arespective processing subsystem coupled to each of the plurality ofmemory subsystems; wherein each respective processing subsystem isconfigured to execute instructions that are included on the respectivememory subsystem to which it is coupled in order to provide a respectiveapplication; and a multi-endpoint adapter device that is coupled to eachof the respective processing subsystems, wherein the multi-endpointadapter device includes: a respective endpoint device coupled to eachrespective processing subsystem; a plurality of multi-endpoint adapterdevice ports that are coupled to respective external switch device portson an external switch device; and an internal switch device that iscoupled to each of the respective endpoint devices and each of theplurality of multi-endpoint adapter device ports, wherein the internalswitch device is configured to: receive, from a first applicationprovided by a first processing subsystem and through a first endpointdevice, a data packet; match the data packet to a data flow that isidentified in an internal switch device database and that is associatedwith at least one Quality of Service (QoS) parameter; identify a dataflow action that is associated with the data flow in the internal switchdevice database and that provides for the transmission of the datapacket via a first multi-endpoint adapter device port that is includedin the plurality of multi-endpoint adapter device ports and that isconfigured in a manner that satisfies the at least one QoS parameter;and perform the data flow action to transmit the data packet through thefirst multi-endpoint adapter device port to the external switch device.8. The IHS of claim 7, wherein the multi-endpoint adapter deviceincludes: a controller that is coupled to at least one of the pluralityof multi-endpoint adapter device ports, wherein the controller isconfigured to: receive, via at least one of the plurality ofmulti-endpoint adapter device ports and via the external switch device,data flow match information; store the data flow match information inthe internal switch device database, wherein the internal switch deviceis configured to use the data flow match information to match the datapacket to the data flow.
 9. The IHS of claim 7, wherein themulti-endpoint adapter device includes: a controller that is coupled toat least one of the plurality of multi-endpoint adapter device ports,wherein the controller is configured to: receive, via at least one ofthe plurality of multi-endpoint adapter device ports and via theexternal switch device, data flow action information; store the dataflow action information in the internal switch device database, whereinthe internal switch device is configured to identify the data flowaction from the data flow action information.
 10. The IHS of claim 7,wherein the internal switch device is configured to; provide for anegotiation between the first multi-endpoint adapter device port and afirst external switch device port that configures the firstmulti-endpoint adapter device port the manner that satisfies the atleast one QoS parameter.
 11. The IHS of claim 7, wherein the matchingthe data packet to the data flow that is identified in the internalswitch device database includes: identifying a Virtual Local AreaNetwork (VLAN) tag that was provided in the data packet by the firstapplication; matching the VLAN tag to a VLAN tag that is associated withthe data flow in the internal switch device database.
 12. The IHS ofclaim 7, wherein the at least one QoS parameter includes a minimumtransmission speed.
 13. The IHS of claim 7, wherein the at least one QoSparameter includes a maximum latency.
 14. A method for routing packetsin a multi-endpoint adapter/multi-processor system, comprising:receiving, by an internal switch device included in a multi-endpointadapter device from one of a plurality of applications that are eachprovided by a respective one of a plurality of processing subsystemsthat are each coupled to the multi-endpoint adapter device via arespective multi-endpoint adapter device port on the multiple endpointadapter and through one of a plurality of endpoint devices that areincluded on the multi-endpoint adapter device, a data packet; matching,by the internal switch device, the data packet to a data flow that isidentified in an internal switch device database and that is associatedwith at least one Quality of Service (QoS) parameter; identifying, bythe internal switch device, a data flow action that is associated withthe data flow in the internal switch device database and that providesfor the transmission of the data packet via a first multi-endpointadapter device port and that s configured in a manner that satisfies theat least one QoS parameter; and performing, by the internal switchdevice, the data flow action to transmit the data packet through thefirst multi-endpoint adapter device port to the external switch device.15. The method of claim 14, further comprising: receiving, by acontroller that is included in the multi-endpoint adapter device via theexternal switch device and through at least one of the plurality ofmulti-endpoint adapter device ports to which it is coupled, data flowmatch information; storing, by the controller, the data flow matchinformation in the internal switch device database, wherein the internalswitch device is configured to use the data flow match information tomatch the data packet to the data flow.
 16. The method of claim 14,further comprising: receiving, by a controller that is included in themulti-endpoint adapter device via the external switch device and throughat least one of the plurality of multi-endpoint adapter device ports towhich it is coupled, data flow action information; storing, by thecontroller, the data flow action information in the internal switchdevice database, wherein the internal switch device is configured toidentify the data flow action from the data flow action information. 17.The method of claim 14, further comprising: providing, by the internalswitch device, for a negotiation between the first multi-endpointadapter device port and a first external switch device port thatconfigures the first multi-endpoint adapter device port the manner thatsatisfies the at least one QoS parameter.
 18. The method of claim 14,wherein the matching the data packet to the data flow that is identifiedin the internal switch device database includes: identifying a VirtualLocal Area Network (VLAN) tag that was provided in the data packet bythe first application; matching the VLAN tag to a VLAN tag that isassociated with the data flow in the internal switch device database.19. The method of claim 14, wherein the at least one QoS parameterincludes a minimum transmission speed.
 20. The method of claim 14,wherein the at least one QoS parameter includes a maximum latency.